Apparatus and method for procedural operations development and distribution

ABSTRACT

A method includes storing information defining a plurality of procedures to be followed. The method also includes receiving a request for the information associated with at least one of the procedures. The method further includes formatting the requested information based on a platform to receive the requested information. In addition, the method includes providing the formatted requested information to the platform. Formatting the requested information may include formatting the requested information using one of a plurality of templates, where the templates are associated with a plurality of different procedure types. Formatting the requested information may also include formatting the requested information differently based on whether the requested information is to be presented via a console computing device, a mobile device, or a printed document.

TECHNICAL FIELD

This disclosure relates generally to management systems and morespecifically to an apparatus and method for procedural operationsdevelopment and distribution.

BACKGROUND

Organizations such as corporations often define or standardizeprocedures to be followed by employees or other personnel of theorganizations. The procedures could represent any suitable sequence ofsteps required to perform a specific function, satisfy a particularobjective, or otherwise achieve a specified goal. As an example,procedures could be defined to specify how particular operations in apetrochemical plant should be performed. By standardizing itsprocedures, an organization may encourage the use of streamlined orimproved processes and reduce potential risks.

Even though procedures may be defined or standardized with anorganization, problems may still occur when the procedures are actuallyimplemented. These problems may include personnel failing to comply witha procedure, having an inadequate amount of time to complete aprocedure, having a procedure that is irrelevant to a particular task athand, or having a procedure that is too lengthy or hard to read. Some ofthese problems are based on the ways that procedures are presented andhow the procedures are used. Not all procedures are alike, and aprocedure may have different requirements based on the context of useand the technology being employed.

SUMMARY

This disclosure provides an apparatus and method for proceduraloperations development and distribution.

In a first embodiment, a method includes storing information defining aplurality of procedures to be followed. The method also includesreceiving a request for the information associated with at least one ofthe procedures. The method further includes formatting the requestedinformation based on a platform to receive the requested information. Inaddition, the method includes providing the formatted requestedinformation to the platform.

In particular embodiments, formatting the requested information includesformatting the requested information using one of a plurality oftemplates, where the templates are associated with a plurality ofdifferent procedure types.

In other particular embodiments, formatting the requested informationincludes formatting the requested information differently based onwhether the requested information is to be presented via a consolecomputing device, a mobile device, or a printed document.

In a second embodiment, an apparatus includes at least one memorycapable of storing information defining one or more procedures to befollowed. The apparatus also includes at least one processor capable ofreceiving a request for the information associated with at least one ofthe procedures, formatting the requested information based on a platformto receive the requested information, and providing the formattedrequested information to the platform.

In a third embodiment, a computer program is embodied on a computerreadable medium and is operable to be executed by a processor. Thecomputer program includes computer readable program code for receiving arequest for information associated with at least one of a plurality ofprocedures to be followed, formatting the requested information based ona platform to receive the requested information, and providing theformatted requested information to the platform.

Other technical features may be readily apparent to one skilled in theart from the following figures, descriptions, and claims.

BRIEF DESCRIPTION OF THE DRAWINGS

For a more complete understanding of this disclosure, reference is nowmade to the following description, taken in conjunction with theaccompanying drawings, in which:

FIG. 1 illustrates an example system for procedural operationsdevelopment and distribution according to one embodiment of thisdisclosure;

FIG. 2 illustrates an example method for procedural operationsdevelopment and distribution according to one embodiment of thisdisclosure;

FIGS. 3A and 3B illustrate example databases for storage anddistribution of procedure-related information according to oneembodiment of this disclosure;

FIG. 4 illustrates additional details of an example system forprocedural operations development and distribution according to oneembodiment of this disclosure; and

FIG. 5 illustrates an example method for creating and storing proceduresaccording to one embodiment of this disclosure.

DETAILED DESCRIPTION

FIG. 1 illustrates an example system 100 for procedural operationsdevelopment and distribution according to one embodiment of thisdisclosure. In the illustrated example, the system 100 includes userdevices 102 a-102 c, a printer 104, a network 106, a procedures server108, and a database 110. Other embodiments of the system 100 may be usedwithout departing from the scope of this disclosure.

In one aspect of operation, personnel use the user devices 102 a-102 c(referred to as “user devices 102”) to access the procedures server 108and the database 110. The procedures server 108 provides a mechanism forcreating, modifying, and deleting procedures to be followed, such asprocedures to be followed in a corporation or other organization. Theinformation associated with the defined procedures is stored in thedatabase 110. Also, personnel may select which platforms (types of userdevices 102) can retrieve particular content from the database 110, andthe format of that content can be controlled based on the platformretrieving the content. Among other things, this may provide a centralrepository for procedure-related information, which may allow easierdefinition, maintenance, access, and use of the procedures.

In the illustrated embodiment, each user device 102 is capable ofcommunicating with the network 106. Each user device 102 represents anysuitable device, system, or portion thereof that allows a user tocommunicate and interact with the procedures server 108. For example, auser device 102 may allow a user to retrieve procedure-relatedinformation from the database 110 so that the user can implement aprocedure. A user device 102 may also allow a user to access or invokean application executed by the procedures server 108 in order to definea new procedure or modify an existing procedure.

In this particular example, the user devices 102 include a desktop,laptop, or other console computer (user device 102 a), a mobiletelephone (user device 102 b), and a handheld computer (user device 102c). Each of these user devices 102 communicates over a wireline orwireless connection. These particular user devices 102 are forillustration only. Any other or additional computing or communicationdevices or platforms may be used in the system 100. Each user device 102includes any hardware, software, firmware, or combination thereof foraccessing or interacting with the procedures server 108.

The printer 104 is coupled to the network 106. The printer 104 allowsusers to print documents containing procedure-related information, suchas MICROSOFT WORD documents, ADOBE PDF documents, or other documents.The printer 104 may represent any suitable printing device, such as astand-alone printer, a combination printer-fax-scanner device or othermulti-function device, or a networked photocopy machine. Although shownas being coupled to the network 106, the printer 104 could be coupleddirectly to a user device 102 or communicate wirelessly with a userdevice 102.

The network 106 is capable of communicating with the user devices 102and the procedures server 108. The network 106 facilitates communicationbetween components of the system 100. For example, the network 106 maycommunicate Internet Protocol (IP) packets, frame relay frames,Asynchronous Transfer Mode (ATM) cells, or other suitable informationbetween network addresses. The network 106 may include one or more localarea networks (LANs), metropolitan area networks (MANs), wide areanetworks (WANs), all or a portion of a global network such as theInternet, or any other communication system or systems at one or morelocations. The network 106 may also operate according to any appropriatetype of protocol or protocols, such as Ethernet, IP, X..25, frame relay,or any other protocol.

The procedures server 108 is coupled to the network 106 and the database110. The procedures server 108 supports the definition and maintenanceof procedures to be followed in an organization. For example, theprocedures server 108 may receive information defining procedures fromusers and store the information in the database 110. The proceduresserver 108 may also allow users to retrieve information associated withprocedures that have been defined and provide that information to theuser devices 102. The procedures server 108 may further allow users tospecify the platforms that can retrieve defined procedures and theformats for those procedures. The procedures server 108 includes anyhardware, software, firmware, or combination thereof for defining,maintaining, or accessing procedure-related information. In particularembodiments, the procedures server 108 includes one or more processors112 and one or more memories 114 containing data and instructions usedby the one or more processors 112.

The database 110 is coupled to the procedures server 108. The database110 stores various information associated with procedures used by anorganization. For example, the database 110 could store procedureinformation 116, which identifies the sequence of steps required toperform a specific function, satisfy a particular objective, orotherwise achieve a specified goal. The database 110 could also storeplatform information 118, which identifies the platforms associated withthe various procedures defined by the procedure information 116. Inaddition, the database 110 could store format information 120, whichidentifies the formats used to present information associated with thevarious procedures.

The database 110 includes any hardware, software, firmware, orcombination thereof for storing and facilitating retrieval ofinformation. Also, the database 110 uses any of a variety of datastructures, arrangements, and compilations to store and facilitateretrieval of information. Although shown as separate pieces ofinformation 116-120 in FIG. 1, the various pieces of information in FIG.1 could be combined or further subdivided according to particular needs.As an example, the procedure information 116, platform information 118,and format information 120 for a single procedure could be storedtogether in the database 110.

In one aspect of operation, users may define procedures to be followedin an organization via the procedures server 108. For example, theprocedures server 108 could execute an application that allows users toprovide procedure-related content (such as a description of proceduresteps), hyperlinks, supporting documentation, conditions, and warningsassociated with a procedure. The application could also allow users toselect the platform(s) that can retrieve procedures and to specifyformatting options for each platform. This information may then bestored in the database 110. In some embodiments, the applicationexecuted by the server 108 receives data about a procedure usingdifferent data-entry fields, where some fields are mandatory (such astop-level steps of the procedure) and other fields are optional (such ashyperlinks to related information).

As a particular example, the procedures server 108 may provide aframework for quantitatively classifying procedures into differentclassifications. The classifying may be based, for example, on thecomplexity of the procedures, the consequences associated with theprocedures, and the frequency of using the procedures. The proceduresserver 108 also allows users to specify whether a classified procedureis available for viewing on a console computer (such as user device 102a), on a mobile device (such as user devices 102 b-102 c), in paper form(such as via printer 104), or in any other or additional manner. Theprocedures server 108 further allows users to specify the format of aprocedure for a particular platform, such as MICROSOFT WORD or ADOBE PDFdocuments for console computers or a human-factored small screen displayfor mobile devices. In some embodiments, the selection of the platformsand formats is based on the context of how a procedure is expected to beused. As an example, procedures employed by personnel working insidebuildings at console computer terminals could have certain platforms andformats specified, while procedures employed by personnel workingoutside in varying locations could have other platforms and formatsspecified.

Although FIG. 1 illustrates one example of a system 100 for proceduraloperations development and distribution, various changes may be made toFIG. 1. For example, the system 100 may include any number of userdevices 102, printers 104, networks 106, servers 108, and databases1010. Also, while FIG. 1 illustrates the use of a server 108 in thesystem 100, the functionality of the server 108 could be implemented onother device(s), such as a desktop computer or a laptop computer.Further, while FIG. 1 illustrates that one database 110 is coupleddirectly to the procedures server 108, any number of databases 110 mayreside at any location or locations accessible by the server 108. Inaddition, while FIG. 1 illustrates one operational environment in whichprocedural operations development and distribution could occur, theprocedural operations development and distribution mechanism could beused in any other suitable device or system.

FIG. 2 illustrates an example method 200 for procedural operationsdevelopment and distribution according to one embodiment of thisdisclosure. The method 200 shown in FIG. 2 is for illustration only.Other embodiments of the method 200 could be used without departing fromthe scope of this disclosure. Also, for ease of explanation, the method200 is described with respect to the system 100 of FIG. 1. The method200 could be used with any other suitable device or system.

The method 200 operates by receiving various inputs 202, which representinformation associated with a procedure being defined. In this example,the inputs 202 include information about the procedure itself, one ormore analyses about the plant or facility in which the procedure is tobe used (such as a Hazards and Operability or “HAZOP” analysis), andinformation from experts.

These inputs 202 are used to make assessments 204 of various riskfactors associated with the procedure being defined. In this example,the assessments 204 include a consequence assessment, a frequencyassessment, and a complexity assessment. The consequence assessmentassesses the potential impact if the procedure is not executed orperformed properly. The consequence assessment could, for example,assess the potential impact on personnel safety, operational integrity,and environment health. The frequency assessment assesses the likelihoodof using the procedure over time. The complexity assessment assesses thelevel of challenge for personnel to successfully perform or implementthe procedure.

Based on the assessments 204, the procedure being defined is classifiedinto one of multiple classifications 206. In this example, theclassifications 206 include a resource classification, a reviewclassification, and an in-task classification. The resourceclassification is associated with procedures having a low impact risk(such as procedures primarily used for initial training or for referenceas a refresher). The review classification is associated with procedureshaving a moderate impact risk that may be reviewed pre-execution andpost-execution. The in-task classification is associated with procedureshaving a significant impact risk. Procedures classified as in-task mayrequire the use of a checklist (such as a list where personnel initialeach step and sign and date the list upon completion of the procedure)and a safety observer or team leader to oversee the execution of theprocedure and verify the appropriate completion of critical activities.

The classification 206 of the procedure being defined is combined withone or more contexts of use 208. The contexts of use 208 identify one ormore contexts in which the procedure could be used. In this example, thecontexts of use 208 include a console context and a field context. Theconsole context of use 208 indicates that the procedure could be used bypersonnel at computer consoles in a control center or other locations ina facility. The field context of use 208 indicates that the procedurecould be used by personnel in the field (such as at or near industrialprocessing equipment). In this example, the contexts of use 208 alsoinclude a paper context and an electronic context. These contexts of use208 identify whether the procedure is used with technology that ispaper-based (procedure is provided to personnel using printed documents)or electronic (procedure is provided to personnel using electronicdevices).

The classification 206 and context(s) of use 208 for the procedure beingdefined are combined and used to identify one or more effectiveinteraction techniques 210. The effective interaction techniques 210represent techniques (whether in paper, electronic, or other form) usedto ensure that personnel effectively execute or implement the procedure.For example, the effective interaction techniques 210 could be used toensure that the appropriate personnel read, verify, and understand theprocedure. The effective interaction techniques 210 could also be usedto ensure that the procedure is executed accurately, efficiently,safely, and economically.

In this example, the various aspects of the effective interactiontechniques 210 include procedure content (information describing theprocedure), procedure structure (the presentation of the procedure), andnavigation (ways a user follows the flow of the procedure and gainsaccess to required information). The various aspects of the effectiveinteraction techniques 210 also include procedure format (thearrangement or organization of the procedure) and terminology (thelanguage used in the procedure). In addition, the various aspects of theeffective interaction techniques 210 include status format (for aprocedure, a step, or part of a step) and data entry (the ways to enterinformation for procedure steps).

The end result of the method 200 is an effective procedure 212, which isa procedure designed for a specific context of use. Informationassociated with the effective procedure 212 could be provided to a userin any suitable manner, such as in printed form or electronically. Theeffective interaction techniques 210 or the effective procedure 212could vary depending on the user receiving the procedure-relatedinformation. For example, the information defining a procedure that ispresented to a user using a console device may differ from theinformation defining the procedure that is presented to a user using amobile device.

The following represents additional details regarding the method 200 ofFIG. 2. These additional details are for illustration and explanationonly. Other embodiments of the method 200 that operate in a differentmanner could be used without departing from the scope of thisdisclosure. As examples, the method 200 could be modified in anysuitable manner, such as by making different assessments 204, usingdifferent classifications 206, identifying different contexts of use208, or selecting different effective interaction techniques 210.

The first part of the method 200 may generally be referred to asprocedure classification, which involves using the inputs 202 to makethe various assessments 204 and select the appropriate classification206. In some embodiments, a procedure may be classified using arisk-based approach. As described above, different assessments 204 aremade of the risks associated with failing to perform a procedure aswritten, and these assessments 204 are used to classify the procedure.The assessments 204 may, for example, involve expert judgments frompersonnel associated with a particular facility in which the procedurecan be performed. As particular examples, the assessments 204 mayinvolve determinations as to the potential amount or severity ofpersonnel injury, environmental release, and economic loss that could beassociated with failing to follow a procedure. The assessments 204 mayalso involve determining the frequency at which a procedure is performed(procedures performed less frequently may generally require more supportsince personnel may be less familiar with the details of the procedure'sexecution). In addition, the assessments 204 may involve determining thecomplexity of a procedure (more complex procedures may generally providemore opportunities for breakdowns in execution of the procedures).

Once the appropriate classification 206 of a procedure is made, theappropriate contexts of use 208 of the procedure are determined. Thecontexts of use 208 include an operator role, which addresses thedifferent needs of console and field operations. Console operationsoften occur within a control room or other location where operators haveaccess to consoles with larger displays and can initiate actions onplant equipment wired to or otherwise in communication with theconsoles. Field operators often move throughout a facility to performvarious tasks, such as equipment monitoring and preventive maintenance.Field operators are typically more constrained in the amount ofinformation that is available to them (such as when the field operatorsuse mobile devices with small display screens, which makes it difficultto view large documents). Field operators also often rely on the consoleoperators for coordination of activities and information. Table 1outlines some of the differences in the needs between console and fieldoperators based on the classification of a procedure.

TABLE 1 Context of Use In-Task Review Resource Console 1) Leading rolein 1) Leading role in 1) Lead procedure procedural execution proceduralexecution 2) Initial response execution individually activity 2) Initialresponse (inform others of 3) Big picture view activity tasks performedneeded to understand 3) Big picture view before and after global contextneeded to they are executed) 4) Time delay shorter understand global 2)Big picture for ability to context view is available execute step 4)Time delay 3) Time to review shorter for ability detail to execute step5) Time to review detail Field 1) Supporting role in 1) Supportingrole 1) Lead procedure procedural execution in procedural execution 2)Activity after execution individually initial response 2) Activity after(inform others of 3) Need to know local initial response tasks performeddependencies on their 3) Need to know before and after actions and localdependencies they are executed) scheduling on their actions 2) Bigpicture requirements and scheduling view is available 4) Time delaylonger requirements; have 3) Time to review for ability to time to seebig detail execute step picture 4) Time delay longer for ability toexecute step 5) Time to review detail

The classification of procedures into the classifications 206 alsoprovides a basis for establishing practices for delivering procedures inwritten form or electronically. With the delivery of procedural contentappropriate to the risk and conditions of use, these practices may helpto minimize the impact of failing to execute a procedure as intended.Table 2 illustrates example user needs related to conditions of useassociated with the three risk categories (complexity, frequency, andconsequences) discussed above. These user needs may influence theselection of specific interaction techniques 210.

TABLE 2 Context of Use In-Task Review Resource Consequence: High MediumLow Risk of need for need to preview need to know if Incident orAccident verification that cautions/warnings activity has been stepscomplete need completed need communication that cautions/warnings stepsare complete need tracking mechanism on status, people, activity needconstraint information (not to exceed limits) Consequence: High(Emergency) Medium-Low Low Time Pressure initial elements varies withnone need to be nature of the completed within process (typically 15minutes try to complete remaining within a shift) elements need to bedone in few hours Medium-Low (Others) varies with the nature of theprocess Frequency Low-High Low-High Low-High need reminder or needreminder or need reminder or refresher refresher depending refresherdepending on on frequency depending on frequency frequency Complexity:Medium-High Low-High Low Length need tracking need tracking assume noshift mechanism for mechanism for change status, people, status, people,activity activity need reminder need reminder (overview - big(overview - big picture) picture) need to see need to see dependenciesdependencies between actions between actions Complexity: Medium-HighMedium-High Low Cognitive may need may need none Workload automationsupport automation support need well- need well- designed displaysdesigned displays to support to support activities activities needtracking need tracking mechanism for mechanism for status, people,status, people, activity activity Complexity: Low-High Low-High Low-HighPhysical need good need good need good Workload understanding ofunderstanding of understanding of facility layout or facility layout orfacility layout or display display display organization to organizationto organization to minimize minimize minimize unnecessary unnecessaryunnecessary movements movements movements need to look need to look needto look ahead at upcoming ahead at upcoming ahead at upcoming steps toplan steps to plan steps to plan efficient execution efficient executionefficient execution Complexity: High Medium Low Coordination need toneed to need to know Requirements communicate with communicate withinactivity started other disciplines own team and completed in addition toown need to preview team who does what need for need to track automationsupport completion of steps to communications need tracking mechanismfor status, people, activity

Once the appropriate classification 206 and contexts of use 208 of aprocedure are determined, one or more effective interaction techniques210 for the procedure are identified. These techniques 210 may be usedto ensure that procedure-related information is provided to personnel inan appropriate manner given factors such as the context of use 208 (forexample, whether a field operator or console operator has requested theinformation).

When designing a mechanism for effective interaction with a procedure, anumber of content and form options may be considered and selected basedon the procedure classification 206 and the context(s) of use 208. Thecontent and form options may include procedure content, procedurestructure, navigation, procedure format, terminology, status format, anddata entry.

The classification 206 and contexts of use 208 may determine theprocedure content to be provided to personnel requesting informationabout a procedure. For example, in a time-pressure situation, personnelmay not have time to read large amounts of detail regarding a procedure.Key steps could be salient so they are not missed, and checklists may beuseful here. As another example, it is often difficult to read andscroll text describing a procedure on a handheld mobile device (comparedwith text presented on paper or a console display), so the contentprovided to the user may differ depending on the platform being used bythe user.

In particular embodiments, the procedure content may include informationsuch as the steps or actions of a procedure, the number of steps oractions, and notes, cautions, warnings, and hazards associated with theprocedure. The procedure content could also include relatednon-procedural information, such as document information (document type,revision number, revision date, author, and reviewer), background,purpose, and related references.

The classification 206 and contexts of use 208 may also determine thestructure of a procedure (how procedure-related information is providedto personnel requesting information about a procedure). In particularembodiments, a procedure could have a hierarchical organization or aflat organization. A hierarchical organization divides the procedureinto manageable pieces or modules. This may make it easier for anoperator to scan, understand, and remember the procedure. A flatorganization keeps the steps of a procedure at one level. This may workbetter for shorter procedures or checklists where operators can quicklynavigate to the required steps without going through a hierarchicalstructure, and interdependencies among steps can be readily shown.

The classification 206 and contexts of use 208 may further determine thenavigation techniques available to personnel requesting informationabout a procedure. The ability to easily navigate within and acrossprocedures may minimize user error, minimize user frustration, anddecrease the overall time for executing the procedures. Different typesof navigation could be available for use by personnel requestingprocedure-related information. For example, global navigation mayprovide a broad sweep of an entire procedure and bring together accesspoints that operators may use to move from one part of the procedure toanother. Local navigation may provide access to procedure steps andrelated information associated with what the operators are currentlydoing (such as providing access to parent, sibling, and children modulesof the current module being executed in a hierarchically arrangedprocedure). Supplementary navigation may provide shortcuts to relatedcontent not readily accessible through global or local navigation.Contextual navigation may be embedded in the content of a procedure orstep and include hyperlinks to supporting information. Courtesynavigation may provide access to information users do not need on aregular basis but that is provided as a convenience.

Specific forms of navigation could be provided to operators to navigatethe procedure content. These include an overview navigation map, whichprovides high-level procedure structure information and graphics (suchas nodes or icons) that can be selected to display associated proceduraldetails or instructions. Operators can see how the nodes or icons relateto each other and can navigate to various parts of the procedure.Scrolling (where a user uses a scroll bar or “page up” and “page down”buttons) and tabs (where a procedure is organized into differentsections accessed by tabs) could also be used. In addition, hierarchicallinks (used to navigate a hierarchical organization of a procedure),hypertext/hyperlinks, and menus could be used to navigate procedurecontent.

The classification 206 and contexts of use 208 may also determine theformat of procedure-related information provided to personnel requestinginformation about a procedure. For example, a procedure could beformatted using sections and headings, where sections of the procedurecontent are labeled using section headings. This format may typically beused with paper-based procedures. A procedure could also be formatted asa checklist, which provides a short list of procedure steps that aretypically checked off once completed. A procedure could further beformatted as an overview flowchart, or a graphical flowchart thatconveys the global structure of the procedure with step flow anddependencies. In addition, a procedure could be formatted as a “bymemory” procedure. This format may require that operators memorize atleast some of the procedure steps, such as the first few steps of theprocedure. In certain cases (such as emergencies), operators may nothave time to look up a checklist or regularly formatted procedure, sothe operators may memorize a small number of steps (such as five to ninesteps). The number of memorized steps is typically small, and the numberof procedures requiring memorization of steps is typically small. Thishelps to reduce the likelihood of operator error, such as forgetting astep or confusing steps from different memorized procedures.

The classification 206 and contexts of use 208 may further determine theterminology of the procedure-related information provided to personnelrequesting information about a procedure. For example, the terminologycould include plain language with known reference items, where fullexplanations provide greater detail about the required tasks of aprocedure, any associated references, and any cautions, warnings, orother notes. The terminology could also include short direct language,where short descriptors and symbols are used to convey a procedure orchecklist step to reduce the space and time needed to use theinformation.

Beyond that, the classification 206 and contexts of use 208 maydetermine the status format to be used in procedure-related informationprovided to personnel requesting information about a procedure. Thestatus format identifies how the status of a procedure, step, or partthereof is conveyed. For example, a text message or brief descriptorcould be used to identify the status of a procedure or step. An overviewcould provide a high-level diagram or structure showing the status ofdifferent parts of the procedure, as well as alarms, alerts, andmessages. Symbols or icons could convey the status of a step, activity,outcome, or procedure state. Graphics and figures could be used to showactivities or dynamic variables. Photos and video could provide directdisplay of remote locations and can be used to verify steps and states.Color (with any of the items noted above) can be used to effectivelyconvey the status or importance of information.

In addition, the classification 206 and contexts of use 208 maydetermine the data entry used with the procedure being requested bypersonnel. Various data entry devices or techniques could be used with aprocedure. For example, automatic data entry could occur using devicessuch as data collection probes or sensors. Automatic calculations onvariables of interest in the procedure could also be done to generatenecessary data. Further, input devices such as a stylus could be used toallow an operator to enter information manually or to select appropriateresponses from a form-based widget (such as a drop-down box). Inaddition, a keyboard could be used by an operator to type in therequired information.

Once the effective interaction techniques 210 are identified, aneffective procedure 212 is produced for a specific context of use, wherethe effective procedure 212 is provided to the personnel requesting aprocedure. The effective procedures 212 provided to different personnelcould vary, even if the effective procedures 212 relate to the samegeneral procedure. The effective procedures 212 could vary, for example,depending on the context of use 208 (such as when one operator is aconsole operator and another operator is a field operator). In someembodiments, different delivery options could be used to provide theeffective procedures 212 to the appropriate personnel. These deliveryoptions include paper-based delivery, on-line static delivery, on-lineinteractive delivery, and on-line hybrid delivery.

Examples of the storage and distribution of procedure-relatedinformation in the database 110 are shown in FIGS. 3A and 3B. Inparticular, FIG. 3A illustrates the use of a centralized database, andFIG. 3B illustrates the use of a distributed database. With thecentralized database 110 shown in FIG. 3A, procedure-related content andinformation for configuring a procedure are entered at one sourcelocation (server 108). The information for configuring a procedure couldbe received by having a user check off items to be shown on paper,console, or mobile devices. This may be done, for example, using anapplication executed on the server 108.

Templates 302 a-302 c are used to format procedure-related informationfrom the database 110 for presentation to users using the user devices102. Each of the templates 302 a-302 c may format information associatedwith a different type of procedure or platform. For example, one or moretemplates 302 a may be used to format information associated withpaper-based or static on-line procedures. One or more templates 302 bmay be used to format information associated with procedures for mobiledevices. One or more templates 302 c may be used to format informationassociated with semi-automated procedures. Semi-automated proceduresrepresent procedures that are partially implemented using programmingcode. The particular template used to format a specific procedure may bechosen based on the procedure type, the implementation medium, and thecontext of use of the procedure.

The templates 302 a-302 c are used to provide procedures 304 a-304 c,respectively, to users. For example, procedures 304 a representprocedures provided in paper-based form (printed onto paper) or staticon-line form (viewed electronically using console computers or otherdevices). Procedures 304 b represent procedures for mobile devices,which may be configured for use with devices having small displayscreens (making it difficult to present large amounts of information) orlimited input/output functionality (meaning specialized navigationfunctions are needed). Procedures 304 c represent programming code forsemi-automated procedures.

The paper-based procedures 304 a are generally made available topersonnel in an organization for printing. The static on-line procedures304 a are generally made available in electronic form to personnel inthe organization when requested. The procedures 304 b for mobile devicesare generally made available to mobile devices when needed. Theprocedures 304 b may also interact with the procedures 304 c toimplement any necessary automated functionality required by theprocedures 304 b. The procedures 304 b may further interact with a planthistorian 306, which archives information about the procedures 304 b(such as who invoked the procedures 304 b and the interactions with theprocedures 304 c). The procedures 304 c may interact with the procedures304 b, the plant historian 306, and a distributed control system 308.The distributed control system 308 represents a control system capableof performing the functions implemented or invoked by the procedures 304c.

As shown in FIG. 3B, the use of a distributed database 110 could also besupported in the system 100. This may be useful, for example, whenexisting infrastructure at a facility requires a distributed databasearrangement, where a primary database calls procedures in otherdatabase(s). In this example, the procedures 304 b for mobile devicescan be accessed via a database 350, which provides access to a procedure304 b using an identified procedure call configuration. In this way,procedures may be linked and called upon as appropriate. Templates 304a-304 c could still be used for each delivery option and procedure type.

The following represents particular details of how procedures in thedatabase 110 may be formatted and presented to different platforms.These particular details are for illustration and explanation only andare not meant to limit the scope of this disclosure. In the followingdescription, the procedures may be provided to personnel usingpaper-based delivery, on-line static delivery, on-line interactivedelivery, or on-line hybrid delivery.

Paper-based procedures are often delivered by printing procedure-relatedinformation from the database 110 and placing the printed documents in abinder. Table 3 illustrates how non-procedural content retrieved fromthe database 110 can be formatted for printing based on the differentclassifications 206 of procedures.

TABLE 3 Non-Procedure Content Item In-task Review Resource DocumentInfo: Written clearly on Written clearly on Written clearly ProcedureType all pages and cues all pages and cues all pages and cues insubsequent in subsequent in subsequent pages pages pages Document Info:Document info Document info Document info Process Unit or Area section;tab section; tab section; tab Document Info: Supplementary SupplementarySupplementary Revision Info (Date, #) information informationinformation Document Info: All pages All pages All pages ProcedureReference # Document Info: All pages All pages All pages Number of PagesDocument Info: Supplementary Supplementary Supplementary ProcedureAuthor information information information Document Info: SupplementarySupplementary Supplementary Procedure Reviewers information; mayinformation information not be needed Document Info: Title All pages Allpages All pages General Info: Objective Beginning Beginning Beginning(purpose, desired results, how actions create desired results) GeneralInfo: Safety Beginning Beginning Beginning Precautions (safe workguidelines, special equipment, hazards, environmental concerns, MSDS)General Info: Beginning Beginning Beginning Prerequisites to Execution(tasks to complete, required equipment or process conditions) GeneralInfo: Beginning or Beginning or Beginning or Restrictions or before stepbefore step before step Constraints (process or equipment limitations)Supporting Info: End; or point to End; or point to End; or point toIllustrations (drawings reference docs reference docs reference docs orenhanced images to support actions) Supporting Info: Pointer to docsPointer to docs Pointer to docs References (related procedures, relateddocuments: MOC deviations, operating manuals, MSDS, key processvariables) Supporting Info: End End End Appendices (troubleshootingguide, explanatory materials)

Table 4 illustrates how procedural content retrieved from the database110 can be formatted for printing based on the different classifications206 of procedures.

TABLE 4 Procedure Content Item In-task Review Resource ProcedureInstruction: At step At step At step Step or Action # ProcedureInstruction: Yes Yes Yes Step Description Procedure Instruction: No; butaccess to Yes Yes Action Description it Procedure Instruction: MinimizeDepends, maybe Depends, maybe at Notes at step step ProcedureInstruction: Before step Before step Before step Cautions ProcedureInstruction: Before step Before step Before step Warnings ProcedureInstruction: Before step Before step Before step Hazards (per HAZOP)Procedure Instruction: Indicate as Indicate as Indicate as Roleresponsible for step different column different column different columnor action beside step; use beside step; use beside step; use of color ofcolor of color Procedure Instruction: Within step Within step Withinstep Change process or instruction; use instruction; use instruction;use equipment to specific direct language direct language directlanguage state or condition Procedure Instruction: Within step Withinstep Within step Verify process or instruction; use instruction; useinstruction; use equipment condition exists direct language directlanguage direct language Procedure Instruction: Within step Within stepWithin step Check for malfunction or instruction; use instruction; useinstruction; use abnormal condition direct language direct languagedirect language Procedure Instruction: Within step Within step Withinstep Obtain resource for future instruction; use instruction; useinstruction; use step direct language direct language direct languageProcedure Instruction: Within step Within step Within step Notify aspecific location instruction; use instruction; use instruction; use orjob position direct language direct language direct language ProcedureInstruction: Within step Within step Within step Obtain information frominstruction; use instruction; use instruction; use specific location orjob direct language direct language direct language position ProcedureDocumentation: Yes Maybe No Step or Action Sign off ProcedureDocumentation: Yes Maybe Maybe Step or Action Check-off ProcedureDocumentation: At end At end Logbook Signature on completed procedureProcedure Documentation: Yes if time Yes at step Not required Recordstep completion time Procedure Documentation: At step At step Atstep/data Record process condition logsheet or data associated with stepor action completion

Table 5 illustrates the various interaction techniques 210 available forpaper-based procedures based on the different classifications 206 ofprocedures.

TABLE 5 Interaction In-Task Review Resource Procedure Structure 1 level(flat), but 2 levels 2 levels access to other levels; abbreviatedversion of procedure Navigation to Quick access; at In binder, use of Inbinder, use of Procedure console, intranet tabs, or intranet tabs, orintranet Navigation between None, should be Overview map; Overview map;steps and other items direct and section headings section headingssequential Procedure Format Memory (emergency), Checklist and Checklistand checklist 1^(st)/2^(nd) level action 1^(st)/2^(nd) leveldescriptions; action flowchart if there descriptions; are complexflowchart if there dependencies are complex FIELD: Use of dependencieschecklists or FIELD: Use of logsheets; take out checklists or relevantparts of logsheets the procedure Terminology Short; direct; use Short;direct; use Short; direct; use of standard of standard of standardvocabulary; set vocabulary; set vocabulary; set number of terms numberof terms number of terms used in consistent used in consistent used inconsistent way; no ambiguity way; no ambiguity way; no ambiguity in verbaction in verb action in verb action Status Format Checkoffs/signoffs;Checkoffs/signoffs; Checkoffs; data data values at data values at valuesat instruction or instruction or instruction or summary area summaryarea summary area, logsheet Data Entry Pen Pen PenThe language and terms used in procedures (including paper-basedprocedures) may be consistent across all media. The language may be asshort and direct as possible with no ambiguity for qualified personnel,and facility or organization conventions may be used when designingprocedures. Each lowest-level step of a procedure could be limited toone action plus any associated conditional statements. Bold or othercharacter differentiators may be used for salience (such as boldingaction terms), and text should be easily readable.

Paper-based procedures may have different organizations depending on thepractices of individual facilities or organizations. Also, manypaper-based procedures are performed sequentially, although deviationsfrom the sequence are possible, and other options include steps done inany order, simultaneously, when preconditions are met, or afterbranching. Overview maps may be used for more complex interactions.Hierarchical paper-based procedures often have two levels, a higherlevel and a lower level with more detail. Section headings andindentations may be used to clearly differentiate levels, or multiplecolumns could be used to differentiate levels. Paper-based procedurescan be formatted in any suitable manner, such as by using textdescriptions, icon symbols, and overview diagrams (such as fish-bonediagrams). Overview diagrams may be useful, for example, when the numberof level steps is high (such as 5-10 steps or more), there are complexdependencies, multiple procedures are tied together, timing andcoordination issues exist, or there is a need to show timing issues andcoordination.

Paper-based procedures often include places in the procedures to showroles associated with various coordination requirements. This may beshown as a column beside procedure steps. Text fields for outlining whois responsible for performing an action and/or visual coding (such ascolor) to distinguish different roles could be used. A “pocketchecklist” (short checklist) could also be used to provide informationabout required roles. Paper-based procedures could also includelocations for “checkoffs” (indications that steps are complete) and“signoffs” (approvals from appropriate personnel). Signoffs may benecessary for actions that have high consequences if not performedproperly or that need validation. Signoffs could, for example, be usedfor individual steps of an in-task procedure or for an entire reviewprocedure. The status of individual steps in a paper-based procedurecould be updated using checkoffs and signoffs, state information may beentered into appropriate fields in paper documents, and calculations areoften performed manually. Any warnings (such as warnings of personalinjury) or cautions (such as cautions of equipment damage) may appearbefore a particular step or procedure section. Warnings and cautions maybe distinguishable visually, such as by using double borders forwarnings, single borders for cautions, and/or colors and symbols.Supporting material may be placed at the end of a paper-based procedurefor reference. If it is difficult to access supplementary informationand that information does not change frequently, a copy of theinformation could be included with the paper-based procedure itself.

The above description may be more specific to paper-based proceduresused in the console context of use 208. In the field context of use 208,paper-based procedures (such as review and resource procedures) maysimply include a checklist that is more convenient for use than aconsole paper-based procedure.

Static on-line procedures are typically delivered electronically toconsoles and other computing devices from the database 110. Staticon-line procedures may be in any electronic form, such as MICROSOFT WORDdocuments or ADOBE PDF files that can be browsed and reviewed. Staticon-line procedures are typically navigated using hyperlinks and cues.The requirements for static on-line procedures may be the same as orsimilar to the requirements for paper-based procedures (except thatnavigation is electronic). Documentation and supplementary informationmay be provided through, for example, hypertext or “right-mouse click”functionality. In addition, information can be typed in and saved. Table6 illustrates how non-procedural content retrieved from the database 110can be formatted for static on-line delivery based on the differentclassifications 206 of procedures.

TABLE 6 Non-Procedure Content Item In-task Review Resource DocumentInfo: Clearly visible on Clearly visible on Clearly visible on ProcedureType all pages and cues all pages and cues all pages and cues insubsequent in subsequent in subsequent pages pages pages Document Info:Document info Document info Document info Process Unit or Area section;tab section; tab section; tab Document Info: Revision SupplementarySupplementary Supplementary Info (Date, #) information; information;information; Document info Document info Document info section; tabsection; tab section; tab Document Info: Document info Document infoDocument info Procedure Reference # section; tab section; tab section;tab Document Info: # steps; pages may # steps; pages may # steps; pagesmay Number of Pages not be relevant not be relevant not be relevant foronline version for online version for online version Document Info:Supplementary Supplementary Supplementary Procedure Author information;information; information; Document info Document info Document infosection; tab section; tab section; tab Document Info: SupplementarySupplementary Supplementary Procedure Reviewers information; mayinformation; information; not be needed Document info Document infosection; tab section; tab Document Info: Title All pages All pages Allpages General Info: Objective Beginning; general Beginning; generalBeginning; general (purpose, desired info tab info tab info tab results,how actions create desired results) General Info: Safety Beginning;general Beginning; general Beginning; general Precautions (safe workinfo tab info tab info tab guidelines, special equipment, hazards,environmental concerns, MSDS) General Info: Beginning; generalBeginning; general Beginning; general Prerequisites to info tab info tabinfo tab Execution (tasks to complete, required equipment or processconditions) General Info: Beginning; general Beginning; generalBeginning; general Restrictions or info tab; before info tab; beforeinfo tab; before Constraints (process or step step step equipmentlimitations) Supporting Info: Hypertext links Hypertext links Hypertextlinks Illustrations (drawings or enhanced images to support actions)Supporting Info: Hypertext links Hypertext links Hypertext linksReferences (related procedures, related documents: MOC deviations,operating manuals, MSDS, key process variables) Supporting Info:Hypertext links; Hypertext links; Hypertext links; Appendices tabs tabstabs (troubleshooting guide, explanatory material)

Table 7 illustrates how procedural content retrieved from the database110 can be formatted for static on-line delivery based on the differentclassifications 206 of procedures.

TABLE 7 Procedure Content Item In-task Review Resource ProcedureInstruction: At step At step At step Step or Action # ProcedureInstruction: Yes Yes Yes Step Description Procedure Instruction: No; butaccess to Yes Yes Action Description it Procedure Instruction: MinimizeDepends, maybe at Depends, maybe at Notes step step ProcedureInstruction: Before step Before step Before step Cautions ProcedureInstruction: Before step Before step Before step Warnings ProcedureInstruction: Before step Before step Before step Hazards (per HAZOP)Procedure Instruction: Indicate as Indicate as Indicate as Roleresponsible for different column different column different column stepor action beside step; use beside step; use beside step; use of color ofcolor of color Procedure Instruction: Within step Within step Withinstep Change process or instruction; use instruction; use instruction;use equipment to specific direct language direct language directlanguage state or condition Procedure Instruction: Within step Withinstep Within step Verify process or instruction; use instruction; useinstruction; use equipment condition direct language direct languagedirect language exists Procedure Instruction: Within step Within stepWithin step Check for malfunction or instruction; use instruction; useinstruction; use abnormal condition direct language direct languagedirect language Procedure Instruction: Within step Within step Withinstep Obtain resource for instruction; use instruction; use instruction;use future step direct language direct language direct languageProcedure Instruction: Within step Within step Within step Notify aspecific instruction; use instruction; use instruction; use location orjob position direct language direct language direct language ProcedureInstruction: Within step Within step Within step Obtain information frominstruction; use instruction; use instruction; use specific location orjob direct language direct language direct language position ProcedureDocumentation: Yes Maybe No Step or Action Sign off ProcedureDocumentation: Yes Maybe Maybe Step or Action Check-off ProcedureDocumentation: At end At end Maybe Signature on completed procedureProcedure Documentation: Yes if time Yes at step Not required Recordstep completion time Procedure Documentation: At step At step At stepRecord process condition or data associated with step or actioncompletion

Table 8 illustrates the various interaction techniques 210 available forstatic on-line procedures based on the different classifications 206 ofprocedures.

TABLE 8 Interaction In-Task Review Resource Procedure Structure 1 level(flat) 2 levels 2 levels Navigation to Quick access; at intranetintranet Procedure console, intranet Navigation between None, should beOverview map; Overview map; section steps and other items direct andsection headings; headings; tabs sequential tabs Procedure FormatMemory, checklist Checklist and 1^(st)/2^(nd) Checklist and1^(st)/2^(nd) level action level action descriptions; descriptions;flowchart if there flowchart if there are complex are complexdependencies dependencies Terminology Short, direct Short, direct Short,direct Status Format Checkoffs/signoffs; Checkoffs/signoffs; Checkoffs;data data values at data values at values at instruction instruction orinstruction or or summary area summary area summary area Data EntryStylus, keyboard; Stylus, keyboard; Stylus, keyboard; input devices,input devices, input devices, calculated calculated calculated

The above description may be more specific to static on-line proceduresused in the console context of use 208. In the field context of use 208,field personnel may have handheld computers or other small mobiledevices for viewing and entering information, thereby limiting what thepersonnel can view and enter. Supplementary information could beaccessed with different tabs, and the checklist format may be the mostfeasible or useful. Second-level action descriptions, notes, and otherinformation could be accessed by a details screen, and automated inputdevices in the field may be preferable or desirable if keyboards areawkward to use.

Interactive on-line procedures are typically delivered electronically toconsoles and other computing devices from the database 110. Interactiveon-line procedures may represent procedures that are updated usinginformation from the plant historian 306, and automated workflows may becapable of handling exceptions that arise during execution of theprocedures. Interactive on-line procedures are typically navigated usinghyperlinks and cues. Status updates can be received from the system 100,any necessary calculations can be made by the system 100, and signoffsand checkoffs can be made electronically and tracked. Branching andexception handling could be driven by manual actions and checkoffs, andpotential troubleshooting support can be obtained by showing activityand state information. Many of the requirements for interactive on-lineprocedures may be the same as or similar to the requirements for staticon-line procedures, although several enhancements to aid in procedureexecution can be made. For example, status information about theprocedure and the process of executing the procedure may be available toan operator. Also, the status can be automatically updated based oncheckoffs or signoffs, and any preconditions can be assessedautomatically based on the status. In addition, data can be entered andcalculations can be made automatically, and the distributed controlsystem 308 could be integrated for a particular action. Table 9illustrates how non-procedural content retrieved from the database 110can be formatted for interactive on-line delivery based on the differentclassifications 206 of procedures.

TABLE 9 Non-Procedure Content Item In-task Review Resource DocumentInfo: Clearly visible on Clearly visible on Clearly visible on ProcedureType all pages and cues all pages and cues all pages and cues insubsequent in subsequent in subsequent pages pages pages Document Info:Document info Document info Document info Process Unit or Area section;tab section; tab section; tab Document Info: Supplementary SupplementarySupplementary Revision Info (Date, #) information; information;information; Document info Document info Document info section; tabsection; tab section; tab Document Info: Document info Document infoDocument info Procedure Reference # section; tab section; tab section;tab Document Info: # steps; pages may # steps; pages may # steps; pagesmay Number of Pages not be relevant not be relevant not be relevant foronline version for online version for online version Document Info:Supplementary Supplementary Supplementary Procedure Author information;information; information; Document info Document info Document infosection; tab section; tab section; tab Document Info: SupplementarySupplementary Supplementary Procedure Reviewers information; mayinformation; information; not be needed Document info Document infosection; tab section; tab Document Info: Title All pages All pages Allpages General Info: Objective Beginning; general Beginning; generalBeginning; general (purpose, desired info tab info tab info tab results,how actions create desired results) General Info: Safety Beginning;general Beginning; general Beginning; general Precautions (safe workinfo tab info tab info tab guidelines, special equipment, hazards,environmental concerns, MSDS) General Info: Beginning; generalBeginning; general Beginning; general Prerequisites to info tab info tabinfo tab Execution (tasks to complete, required equipment or processconditions) General Info: Beginning; general Beginning; generalBeginning; general Restrictions or info tab; before info tab; beforeinfo tab; before Constraints (process or step step step equipmentlimitations) Supporting Info: Hypertext links Hypertext links Hypertextlinks Illustrations (drawings or enhanced images to support actions)Supporting Info: Hypertext links Hypertext links Hypertext linksReferences (related procedures, related documents: MOC deviations,operating manuals, MSDS, key process variables) Supporting Info:Hypertext links; Hypertext links; Hypertext links; Appendices tabs tabstabs (troubleshooting guide, explanatory material)

Table 10 illustrates how procedural content retrieved from the database110 can be formatted for interactive on-line delivery based on thedifferent classifications 206 of procedures.

TABLE 10 Procedure Content Item In-task Review Resource ProcedureInstruction: At step At step At step Step or Action # ProcedureInstruction: Yes Yes Yes Step Description Procedure Instruction: No; butaccess to Yes Yes Action Description it Procedure Instruction: MinimizeDepends, maybe at Depends, maybe at Notes step step ProcedureInstruction: Before step Before step Before step Cautions ProcedureInstruction: Before step Before step Before step Warnings ProcedureInstruction: Before step Before step Before step Hazards (per HAZOP)Procedure Instruction: Indicate as Indicate as Indicate as Roleresponsible for step different column different column different columnor action beside step; use beside step; use beside step; use of color ofcolor of color Procedure Instruction: Within step Within step Withinstep Change process or instruction; use instruction; use instruction;use equipment to specific direct language direct language directlanguage state or condition Procedure Instruction: Within step Withinstep Within step Verify process or instruction; use instruction; useinstruction; use equipment condition direct language direct languagedirect language exists Procedure Instruction: Within step Within stepWithin step Check for malfunction or instruction; use instruction; useinstruction; use abnormal condition direct language direct languagedirect language Procedure Instruction: Within step Within step Withinstep Obtain resource for instruction; use instruction; use instruction;use future step direct language direct language direct languageProcedure Instruction: Within step Within step Within step Notify aspecific instruction; use instruction; use instruction; use location orjob position direct language direct language direct language ProcedureInstruction: Within step Within step Within step Obtain information frominstruction; use instruction; use instruction; use specific location orjob direct language direct language direct language position ProcedureDocumentation: Yes Maybe No Step or Action Sign off ProcedureDocumentation: Yes Maybe Maybe Step or Action Check-off ProcedureDocumentation: At end At end Maybe Signature on completed procedureProcedure Documentation: Yes if time Yes at step Not required Recordstep completion time Procedure Documentation: At step; could be At step;could be At step; could be Record process condition automaticallyautomatically automatically or data associated with entered enteredentered step or action completion

Table 11 illustrates the various interaction techniques 210 availablefor interactive on-line procedures based on the differentclassifications 206 of procedures.

TABLE 11 Interaction In-Task Review Resource Procedure Structure 1 level(flat) 2 levels 2 levels Navigation to Quick access; at intranet Inbinder or Procedure console, intranet intranet Navigation between None,should be Overview map; Overview map; steps and other items direct andsection headings; section headings; sequential tabs tabs ProcedureFormat Memory, checklist Checklist and Checklist and 1^(st)/2^(nd) levelaction 1^(st)/2^(nd) level descriptions; action flowchart if theredescriptions; are complex flowchart if there dependencies are complexdependencies Terminology Short, direct, Short, direct Short, directabbreviated Status Format Checkoffs/signoffs; Checkoffs/signoffs;Checkoffs; data data values at data values at values at instruction orinstruction or instruction or summary area; summary area; summary area;dependencies shown, dependencies shown, dependencies shown, status ofstatus of status of procedure: words procedure: words procedure: wordsicons, color icons, color icons, color Data Entry Stylus, keyboard;Stylus, keyboard; Stylus, keyboard; input devices, input devices, inputdevices, calculated calculated calculated

The above description may be more specific to interactive on-lineprocedures used in the console context of use 208. In the field contextof use 208, field personnel may have handheld computers or other smallmobile devices for viewing and entering information, thereby limitingwhat the personnel can view and enter. Supplementary information couldbe accessed with different tabs, and the checklist format may be themost feasible or useful. Second-level action descriptions, notes, andother information could be accessed by a details screen, and automatedinput devices in the field may be preferable or desirable if keyboardsare awkward to use.

Hybrid on-line procedures are typically delivered electronically toconsoles and other computing devices from the database 110. Hybridon-line procedures may represent procedures that provide feedback on thestatus of the procedures and that can execute actions automatically orwhen initiated by an operator. This may help to provide consistentexecution of action steps and to automatically check preconditionsbefore actions are performed. Table 12 illustrates how non-proceduralcontent retrieved from the database 110 can be formatted for hybridon-line delivery based on the different classifications 206 ofprocedures.

TABLE 12 Non-Procedure Content Item In-task Review Resource DocumentInfo: Clearly visible on Clearly visible on Clearly visible on ProcedureType all pages and cues all pages and cues all pages and cues insubsequent in subsequent in subsequent pages pages pages Document Info:Process Document info Document info Document info Unit or Area section;tab section; tab section; tab Document Info: Revision SupplementarySupplementary Supplementary Info (Date, #) information; information;information; Document info Document info Document info section; tabsection; tab section; tab Document Info: Document info Document infoDocument info Procedure Reference # section; tab section; tab section;tab Document Info: Number # steps; pages may # steps; pages may # steps;pages may of Pages not be relevant not be relevant not be relevant foronline version for online version for online version Document Info:Supplementary Supplementary Supplementary Procedure Author information;information; information; Document info Document info Document infosection; tab section; tab section; tab Document Info: SupplementarySupplementary Supplementary Procedure Reviewers information; mayinformation; information; not be needed Document info Document infosection; tab section; tab Document Info: Title All pages All pages Allpages General Info: Objective Beginning; general Beginning; generalBeginning; general (purpose, desired info tab info tab info tab results,how actions create desired results) General Info: Safety Beginning;general Beginning; general Beginning; general Precautions (safe workinfo tab info tab info tab guidelines, special equipment, hazards,environmental concerns, MSDS) General Info: Beginning; generalBeginning; general Beginning; general Prerequisites to info tab info tabinfo tab Execution (tasks to complete, required equipment or processconditions) General Info: Beginning; general Beginning; generalBeginning; general Restrictions or info tab; before info tab; beforeinfo tab; before Constraints (process or step step step equipmentlimitations) Supporting Info: Hypertext links Hypertext links Hypertextlinks Illustrations (drawings or enhanced images to support actions)Supporting Info: Hypertext links Hypertext links Hypertext linksReferences (related procedures, related documents: MOC deviations,operating manuals, MSDS, key process variables) Supporting Info:Hypertext links; Hypertext links; Hypertext links; Appendices tabs tabstabs (troubleshooting guide, explanatory material)

Table 13 illustrates how procedural content retrieved from the database110 can be formatted for hybrid on-line delivery based on the differentclassifications 206 of procedures.

TABLE 13 Procedure Content Item In-task Review Resource ProcedureInstruction: At step At step At step Step or Action # ProcedureInstruction: Yes Yes Yes Step Description Procedure Instruction: No; butaccess to Yes Yes Action Description it Procedure Instruction: MinimizeDepends, maybe at Depends, maybe at Notes step step ProcedureInstruction: Before step Before step Before step Cautions ProcedureInstruction: Before step Before step Before step Warnings ProcedureInstruction: Before step Before step Before step Hazards (per HAZOP)Procedure Instruction: Indicate as Indicate as Indicate as Roleresponsible for different column different column different column stepor action beside step; use beside step; use beside step; use of color ofcolor of color Procedure Instruction: Within step Within step Withinstep Change process or instruction; use instruction; use instruction;use equipment to specific direct language direct language directlanguage state or condition Procedure Instruction: Within step Withinstep Within step Verify process or instruction; use instruction; useinstruction; use equipment condition direct language direct languagedirect language exists Procedure Instruction: Within step Within stepWithin step Check for malfunction or instruction; use instruction; useinstruction; use abnormal condition direct language direct languagedirect language Procedure Instruction: Within step Within step Withinstep Obtain resource for instruction; use instruction; use instruction;use future step direct language direct language direct languageProcedure Instruction: Within step Within step Within step Notify aspecific instruction; use instruction; use instruction; use location orjob position direct language direct language direct language ProcedureInstruction: Within step Within step Within step Obtain information frominstruction; use instruction; use instruction; use specific location orjob direct language direct language direct language position ProcedureDocumentation: Yes Maybe No Step or Action Sign off ProcedureDocumentation: Yes Maybe Maybe Step or Action Check-off ProcedureDocumentation: At end At end Maybe Signature on completed procedureProcedure Documentation: Yes if time Yes at step Not required Recordstep completion time Procedure Documentation: At step; could be At step;could be At step; could be Record process condition automaticallyautomatically automatically or data associated with entered enteredentered step or action completion

Table 14 illustrates the various interaction techniques 210 availablefor hybrid on-line procedures based on the different classifications 206of procedures.

TABLE 14 Interaction In-Task Review Resource Procedure Structure 1 level(flat) 2 levels 2 levels Navigation to Quick access; at intranet Inbinder or Procedure console, intranet intranet Navigation between None,should be Overview map; Overview map; steps and other items direct andsection headings; section headings; sequential tabs tabs ProcedureFormat Memory, checklist Checklist and Checklist and 1^(st)/2^(nd) levelaction 1^(st)/2^(nd) level descriptions; action flowchart if theredescriptions; are complex flowchart if there dependencies are complexdependencies Terminology Short, direct Short, direct Short, directStatus Format Checkoffs/signoffs; Checkoffs/signoffs; Checkoffs; datadata values at data values at values at instruction or instruction orinstruction or summary area; summary area; summary area; dependenciesshown; dependencies shown; dependencies shown activity shown activityshown Data Entry Stylus, keyboard; Stylus, keyboard; Stylus, keyboard;input devices, input devices, input devices, calculated calculatedcalculated

A procedural overview may be needed for more complex hybrid on-lineprocedures, such as when a hybrid on-line procedure has multipledeviations. Procedural overviews may be similar to process schematics,where objects are task-based and mixed with process states to helpconvey the procedure status. A hybrid on-line procedure may appear to besequential, but it may be able to handle deviations. This may requirethe use of status information and actions that need to be done to reachprocedure objectives.

The above description may be more specific to hybrid on-line proceduresused in the console context of use 208. In the field context of use 208,field personnel might have handheld computers or other small mobiledevices for viewing and entering information, thereby limiting what thepersonnel can view and enter. Supplementary information could beaccessed with different tabs, and the checklist format may be the mostfeasible or useful. Second-level action descriptions, notes, and otherinformation could be accessed by a details screen, and automated inputdevices in the field may be preferable or desirable if keyboards areawkward to use.

The above types of procedures may have specific additional requirementsif the procedures are to be provided to or used with electronic mobiledevices (such as telephones, PDAs, tablets, or other mobile devices).The use of electronic mobile devices may allow, for example, reportingof the status of procedure steps in the field and coordination withother personnel to allow monitoring and tracking. The use of electronicmobile devices also allows personnel to access procedure informationwithout needing to print out the procedure.

With these electronic mobile devices, a procedure could be displayed inits entirety, a selected part of the procedure could be displayed, orone or a few steps of the procedure could be displayed. If the entireprocedure is displayed, various flagged levels could be shown to a user,and an abbreviated form or overview could be displayed if the procedureis lengthy. The overview could be navigated using tabs or othermechanisms. If a selected part of the procedure is shown, thepreconditions and status of the procedure could be displayed. Anabbreviated form or overview could be displayed if the portion of theprocedure is lengthy, and the overview could be navigated using tabs orother mechanisms. If one or a few steps of the procedure are shown, thestep(s) could be displayed with some contextual information (such aspreconditions or time requirements), and the step(s) could be integratedwith other tasks as checkoff items.

Connectivity with an electronic mobile device may vary depending on thesituation. For example, a connection to an electronic mobile device andupdating of procedure information could occur as requested, as one ormore steps are completed, when a change in procedure state occurs, orafter moving into a particular zone. The connection may be made inreal-time, and the connection may allow for a high level of coordinationbetween field personnel and other personnel. The connections anddisconnections of the mobile devices could be provided to fieldoperators and to console operators.

Although FIG. 2 illustrates one example of a method 200 for proceduraloperations development and distribution, various changes may be made toFIG. 2. For example, different assessments 204, classifications 206,contexts of use 208, effective interaction techniques 210, and effectiveprocedures 212 could be used. Although FIGS. 3A and 3B illustrateexamples of databases for storage and distribution of procedure-relatedinformation, various changes may be made to FIGS. 3A and 3B. As anexample, databased having different contents or arrangements could alsobe used.

FIG. 4 illustrates additional details of an example system 100 forprocedural operations development and distribution according to oneembodiment of this disclosure. The additional details shown in FIG. 4are for illustration only.

As shown in FIG. 4, an operator interface 402 allows users to view andinteract with interactive procedures 404 and automated procedures 406.The users could be using user devices 102, such as mobile devices in thefield or personal computers or other console computing devices. A userusing a user device 102 may choose to use interactive procedures 404,automated procedures 406, or both. The operator interface 402 integratesthe functionality of these two procedure types into an effective userinterface framework for conducting procedural operations. Theintegration provides a single operator interface for both manual andautomated step execution. Since the viewing capability on mobile devicesmay be significantly less than on a console or other monitor, theoperator interface 402 may use formats that are designed for theappropriate user devices 102.

The interactive procedures 404 enable personnel to simultaneously viewand interact with procedural instructions. This helps the personnel totrack and report on the status of procedure steps. Historical processdata may be available to assist personnel in understanding the processstatus relevant to a procedural activity. Reminders may be used toenhance the personnel's situational awareness of the need to attend tospecific procedural steps. Links to other related documents andinformation may improve operator efficiency in performing proceduralactivities.

The automated procedures 406 may supplement the interactive procedures404 with additional functionality that integrates distributed controlsystem (DCS) automation. This provides automation capability withprocedural sequence control and control system execution commands.Complex sequence control may be enabled with pre-conditions orpost-conditions based on combinations of process-based or time-basedparameters. The DCS commands can be operator-initiated orsystem-initiated as appropriate.

Dynamic procedures 408 enable context-sensitive or mode-basedmodifications to procedural steps and instructions. This dynamiccapability enables the generation of procedures that have the potentialto change the specific content of a step or the sequence of steps duringthe execution of the procedure. Without interaction with the dynamicprocedures 408, the procedural representations provided by theinteractive procedures 404 and the automated procedures 406 may bestatic. With the addition of the dynamic procedures 408, the proceduralrepresentations can be modified dynamically according to specificconditions, mode-based rules, or performance models. For example, astart-up ramp table may provide the basis for adjusting furnacetemperature set points over a specific period of time. As anotherexample, a mathematical formula may be used for keeping feed rates to areactor adjusted to the available oxygen levels. Any calculationsnecessary for dynamic adjustments could come internally from the dynamicprocedures 408 or from other integrated programs.

A procedure configurator 410 provides an environment to create,transform, and update interactive, semi-automated, dynamic, or other oradditional procedures. The procedure configurator 410 could, forexample, represent a development environment for procedures that isdistinct from an operations environment. The procedure configurator 410may be targeted to individuals who create, transform, and updateprocedures (such as trainers, dedicated procedure writers, supervisors,control engineers, or process engineers). The procedure configurator 410could also track or identify changes that have been made from previousversions of a procedure.

FIG. 5 illustrates an example method 500 for creating and storinginteractive, semi-automated, dynamic, or other procedures, where themethod 500 is used by the procedure configurator 410. As shown in FIG.5, a user defines the structure of a procedure at different hierarchicallevels (such as overview, tasks, and steps) at steps 502-506. In someembodiments, a procedure may have an overview and be formed frommultiple tasks, and each task may involve one or more steps. Inparticular embodiments, the user may be given the option of defining upto n levels within a procedure (such as four levels), although the userdoes not have to use all of the levels.

For each part of the procedure hierarchy, specific configurations andinformation may be entered or imported at steps 508-544. This mayinclude:

Navigation links: The user may define parallel, sequential, and otherlinks for procedure flow at step 508. This could be done using aworkflow visualization tool to map out the procedure flow in a blockdiagram format or by creating links within procedure text.

Assignment of access to people/groups: The user may define whichindividuals and groups can access all or part of the procedure forviewing and/or executing at step 510.

Procedure text: The user may enter the text and labels associated withthe procedure overview, tasks, and steps at step 512. This may be shownas labels in the procedure hierarchy.

Warnings, cautions, notes: Extensive notes for particular steps in theprocedure may be provided to guide operators when deviations occur. Theuser may enter this information in the configurator 410 at theappropriate parts of the procedure hierarchy at steps 514-516.

Reference documents: A large number of procedures reference otherdocuments, such as schematic diagrams, appendices, backgrounds,introductions, related procedures and documents, operating manuals,deviation policies, Management of Change (MOC) information, MaterialSafety Data Sheets (MSDS), and explanatory materials. The user may enterreferences and provide hyperlinks to the reference documentation ifavailable at steps 518-520.

Figures and operating displays: Some procedures reference operatingdisplays and figures. It may be useful to have them readily available tothe operator. The user may enter links to the operating displays andfigures as required for specific steps or parts of the procedurehierarchy at steps 522-524.

Conditional requirements: The user may enter conditions and modes(internally or externally defined) associated with the procedure, tasks,and steps at steps 526-528. These can include:

-   -   preconditions before a step can be performed;    -   conditions that define when a step is complete (text or        automated); or    -   time-based conditions that require procedure steps to be        initiated at particular times or performed within certain time        intervals.

Status, limits, constraints, alerts: The user may define the statusoptions, limits, and constraints associated with the procedure step andany alerts that result in deviations at steps 530-532.

Process values: The user may define which process values need to beavailable in the procedure step at steps 534-538. A placeholder could bedefined for a process value, and a check with the historian 306 may beperformed to ensure the variable is available at the required updatefrequency. If so, a connection may be created from the procedure step tothe historian 306.

Automation of steps: The user may select the steps that are to beautomated and define the control actions, initial conditions, andexecution conditions at steps 540-544. A check with the distributedcontrol system 308 may be performed to ensure that the control actionscan be performed automatically. If so, a connection may be created fromthe procedure step to the distributed control system 308.

After the configurations and information are entered, the procedureconfigurator 410 performs completeness and consistency checks at step546. This is done to help ensure that all required information has beenprovided by the user or imported and that the configurations andinformation are consistent with each other. Once the checks have beenperformed and a successful result obtained, a new procedure is createdand saved in the database 110 at step 548.

The method 500 shown in FIG. 5 may form the basis for performing atleast three different actions: creating new procedures, importingexisting procedures, and updating existing procedures. The creation of anew procedure may follow the same flow as shown in FIG. 5. A user couldenter the appropriate information manually, although various optionscould provide flexibility in entering the information. For example, astep-by-step wizard could show a step-by-step process to the user withexamples and assistance, ask the user questions, and allow the user toenter information in a specific sequence. A direct entry approach couldalso be used, where users can directly navigate to the appropriate areasof the workflow shown in FIG. 5 using menus or navigation buttons.

The importing of existing procedures may be useful because manyfacilities and organizations have invested large amounts of resources intheir current procedure management systems (which typically managestatic procedures contained in word processing documents). A mechanismfor importing existing procedures into the procedure configurator 410may benefit a facility or organization by saving time and money overhaving to re-enter the procedures. The import function may take anexisting static procedure in a standard format (such as a MICROSOFT WORDdocument or ADOBE PDF file) and prompt the user to categorize sectionsor portions of the procedure based on the procedure configurator'soptions in FIG. 5. Once these sections or portions are categorized, theuser can finish the design by creating appropriate links to other partsof the procedure, the historian 306, the distributed control system 308,and other documentation. Consistency and completeness checks may promptthe user to areas that require further input.

More sophisticated import functions could also be used. These couldinclude using tag names, phrases, and styles to automatically categorizethe sections or portions of the imported procedure content. If thestructure of a is static procedure can be inferred with direct transferpoints to the procedure configurator 410, the import process could saveusers significant time.

The updating of existing procedures (such as existing interactive,semi-automated, and dynamic procedures) could involve updatingprocedures already created by the procedure configurator 410. In thisexample, the user may open an existing procedure using the procedureconfigurator 410, make the necessary modifications, perform consistencyand completeness checks, and create a modified procedure.

Although FIG. 4 illustrates additional details of an example system 100for procedural operations development and distribution, various changesmay be made to FIG. 4. For example, other types of procedures (such aspaper-based procedures or static on-line procedures) could be used inthe system 100. Although FIG. 5 illustrates one example of a method 500for creating and storing procedures, various changes may be made to FIG.5. As an example, other methods that use different hierarchies orprocedure-related content could be used to create a procedure.

In some embodiments, various functions described above are implementedor supported by a computer program that is formed from computer readableprogram code and that is embodied in a computer readable medium. Thephrase “computer readable program code” includes any type of computercode, including source code, object code, and executable code. Thephrase “computer readable medium” includes any type of medium capable ofbeing accessed by a computer, such as read only memory (ROM), randomaccess memory (RAM), a hard disk drive, a compact disc (CD), a digitalvideo disc (DVD), or any other type of memory.

It may be advantageous to set forth definitions of certain words andphrases used throughout this patent document. The term “couple” and itsderivatives refer to any direct or indirect communication between two ormore elements, whether or not those elements are in physical contactwith one another. The terms “application” and “program” refer to one ormore computer programs, software components, sets of instructions,procedures, functions, objects, classes, instances, related data, or aportion thereof adapted for implementation in a suitable computer code(including source code, object code, or executable code). The terms“include” and “comprise,” as well as derivatives thereof, mean inclusionwithout limitation. The term “or” is inclusive, meaning and/or. Thephrases “associated with” and “associated therewith,” as well asderivatives thereof, may mean to include, be included within,interconnect with, contain, be contained within, connect to or with,couple to or with, be communicable with, cooperate with, interleave,juxtapose, be proximate to, be bound to or with, have, have a propertyof, or the like. The term “controller” means any device, system, or partthereof that controls at least one operation. A controller may beimplemented in hardware, firmware, software, or some combination of atleast two of the same. The functionality associated with any particularcontroller may be centralized or distributed, whether locally orremotely.

While this disclosure has described certain embodiments and generallyassociated methods, alterations and permutations of these embodimentsand methods will be apparent to those skilled in the art. Accordingly,the above description of example embodiments does not define orconstrain this disclosure. Other changes, substitutions, and alterationsare also possible without departing from the spirit and scope of thisdisclosure, as defined by the following claims.

1. A method, comprising: storing information defining a plurality ofprocedures to be followed; receiving a first request for the informationassociated with at least one of the procedures; formatting the requestedinformation based on a first platform to receive the requestedinformation to produce first formatted requested information, wherein atleast one of a content of the requested information, a structure of therequested information, and a navigation for accessing the requestedinformation is based on the first platform to receive the requestedinformation; providing the first formatted requested information to thefirst platform; receiving a second request for the informationassociated with the at least one procedure; formatting the requestedinformation based on a second platform to receive the requestedinformation to produce second formatted requested information; andproviding the second formatted requested information to the secondplatform; wherein the second formatted requested information for thesecond platform is formatted differently than the first formattedrequested information for the first platform.
 2. The method of claim 1,wherein formatting the requested information to produce the firstformatted requested information comprises selecting which portions ofthe requested information to provide based on the first platform.
 3. Themethod of claim 1, wherein formatting the requested information toproduce the first formatted requested information comprises formattingthe requested information using one of a plurality of templates, theplurality of templates associated with a plurality of differentprocedure types.
 4. The method of claim 1, wherein formatting therequested information to produce the first formatted requestedinformation comprises formatting the requested information based onwhether the requested information is to be presented via a consolecomputing device, a mobile device, or a printed document.
 5. The methodof claim 1, further comprising receiving information defining at leastone of: an overview of the procedure, one or more tasks of theprocedure, and one or more steps of the procedure.
 6. The method ofclaim 5, further comprising receiving information defining at least oneof: one or more links identifying a flow of the procedure; one or moreindividuals or groups allowed to access at least part of the procedure;and one or more warnings, cautions, notes, reference documents, figures,displays, status options, limits, constraints, or alerts associated withthe procedure.
 7. The method of claim 5, further comprising receivinginformation defining at least one of: one or more process variables,each process variable having a value provided during execution of theprocedure; and one or more automated steps to be performed duringexecution of the procedure.
 8. The method of claim 1, wherein storingthe information defining the plurality of procedures comprises storingthe information in a central database.
 9. The method of claim 1, whereina data ently used with the at least one procedure and a status formatidentifying how a status of the at least one procedure is conveyed arebased on the platform to receive the requested information.
 10. Anapparatus, comprising: at least one memory for storing informationdefining one or more procedures to be followed; and at least oneprocessor for: receiving a first request for the information associatedwith at least one of the procedures; formatting the requestedinformation based on a first platform to receive the requestedinformation to produce first formatted requested information, wherein atleast one of a content of the requested information, a structure of therequested information, and a navigation for accessing the requestedinfonmation is based on the first platform to receive the requestedinformation; providing the first formatted requested information to thefirst platform; receiving a second request for the informationassociated with the at least one procedure; formatting the requestedinformation based on a second platform to receive the requestedinformation to produce second formatted requested information; andproviding the second formatted requested information to the secondplatform; wherein the second formatted requested information for thesecond platform is formatted differently than the first formattedrequested information for the first platform.
 11. The apparatus of claim10, wherein the requested information is formatted to produce the firstformatted requested information by selecting which portions of therequested information to provide based on the first platform.
 12. Theapparatus of claim 10, wherein one of a plurality of templates is usedto format the requested information to produce the first formattedrequested information, the plurality of templates associated with aplurality of different procedure types.
 13. The apparatus of claim 10,wherein the requested information is formatted to produce the firstformatted requested information based on whether the requestedinformation is to be presented via a console computing device, a mobiledevice, or a printed document.
 14. The apparatus of claim 10, whereinthe at least one processor is further for receiving information definingat least one of: an overview of the procedure, one or more tasks of theprocedure, and one or more steps of the procedure.
 15. The apparatus ofclaim 14, wherein the at least one processor is further for receivinginformation defining at least one of: one or more process variables,each process variable having a value provided during execution of theprocedure; and one or more automated steps to be performed duringexecution of the procedure.
 16. The apparatus of claim 10, furthercomprising a central database for storing information defining aplurality of procedures including the one or more procedures to befollowed.
 17. A computer program embodied on a computer readable medium,the computer program comprising computer readable program code for:receiving a first request for information associated with at least oneof a plurality of procedures to be followed; formatting the requestedinformation based on a first platform to receive the requestedinformation to produce first formatted requested information, wherein atleast one of a content of the requested information, a structure of therequested information, and a navigation for accessing the requestedinformation is based on the first platform to receive the requestedinformation; providing the first formatted requested information to thefirst platform; receiving a second request for the informationassociated with the at least one procedure; formatting the requestedinformation based on a second platform to receive the requestedinformation to produce second formatted requested information; andproviding the second formatted requested information to the secondplatform; wherein the second formatted requested information for thesecond platform is formatted differently than the first formattedrequested information for the first platform.
 18. The computer programof claim 17, wherein the computer readable program code for formattingthe requested information to produce the first formatted requestedinformation comprises computer readable program code for selecting whichportions of the requested information to provide based on the firstplatform.
 19. The computer program of claim 17, wherein the computerreadable program code for formatting the requested information toproduce the first formatted requested information comprises computerreadable program code for formatting the requested information using oneof a plurality of templates, the plurality of templates associated witha plurality of different procedure types.
 20. The computer program ofclaim 17, wherein the computer readable program code for formatting therequested information to produce the first formatted requestedinformation comprises computer readable program code for formatting therequested information based on whether the requested information is tobe presented via a console computing device, a mobile device, or aprinted document.
 21. The computer program of claim 17, furthercomprising computer readable program code for receiving and storinginformation defining: at least one of: an overview of the procedure, oneor more tasks of the procedure, and one or more steps of the procedure;and at least one of: one or more process variables and one or moreautomated steps to be performed during execution of the procedure, eachprocess variable having a value provided during execution of theprocedure.